%!TEX root = /Users/franciscopereira/nemesisesb/doc/artigo_edoc/bare_conf.tex
This section presents the IT technologies that could form an infra-structure 
to aid the execution of Scientific Police's business process. It presents the 
concept of Enterprise Service Bus (ESB), and furthermore, it presents
a Brazilian government initiative to address inter operability between IT 
systems under government organs.

\subsection{Enterprise Service Bus}
\label{sec:esb}

Enterprise Service Bus (ESB) is an open standards, message based, distributed integration infrastructure that provides routing, invocation and mediation services to facilitate the interactions of disparate distributed applications and services in a secure and reliable manner.


The general goal of the ESB is provide messaging and integration without writing code. And they're a ideal backbone for implementing service oriented architectures, because it provides universal mechanism to interconnect all the services required in the composed business solution without compromising security, reliability, performance and scalability.

According to Falko Menge\cite{ESB1}, ESB typically have the fowling features:

\begin{enumerate}
\item Invocation: the ability to send requests and receive responses from services and resources.
\item Routing: the ability to decide the destination of a message during its transport.
\item Mediation: transformations or translations between disparate resources including transport protocol, message format and message content.
\item Security: provide security for the messages.
\item Management: Audit and logging facilities for monitoring infrastructure and integration scenario and possibly also for controlling process execution.
\item Process Orchestration: engine to execute business processes described with Web Services Business Process Execution Language.
\end{enumerate}

This characteristics, allows the integration of different software components to be integrated with
others components in a standard way. The software pieces integrated in a ESB doesn't require been 
develop in any programing language or any developer.


\subsection{ e-PING (Patterns of Interoperability for Electronic Government)}
\label{sec:eping}
e-PING is an architecture that defines a set of assumptions, policies and technical specification that regulates the utilization of Computer Information Technologies (TIC) in the interoperability of Electronic Government Services\cite{eping},  establishing conditions to iterate with other Government departments and with the society.
The following subjects areas are covered by the e-PING:
\begin{itemize}
 \item Interconnection
 \item Security
 \item Access Point
 \item Organization and Exchange of Information
 \item Integration Areas for Electronic Governments
\end{itemize}

The adhesion for the e-PING is voluntary for the civilians and for several instances of the government, inside and outside the country. But, for the federal government departments (Executive Power) the adoption of the patterns and policies of the e-PING is mandatory. Including the administration departments: Ministries, Departments and other government entity of the same juristic nature, connected directly or indirectly with the Republic Presidency of the Brazil,  authorities and foundation.
%citar as iniciativas relacionadas, como aquele artigo da NSA.


The e-PING standard could be considered as a guideline of standards to be followed to develop
standards addressing the needs of Scientific Police business process. This approach intends to 
simplify the communication between others government organs and the Scientific Police.


The establishment of a Scientific Police's ESB in conformity with the e-PING standard can
lend to several value added features to services\cite{deploying} at the bus.
And it's utilization, besides improve the Police Department efficiency, can provide
important information to state or federal government social acts.   

\section{Scientific Police ESB Requirements}
\label{esb}


To establish a service bus adherent to the Scientific Police's business process its important to map 
the organization requirements that this tool must have. As presented in section \ref{sptc} the
work made in the Scientific police deals with extremely personal information, this fact leads to the
most critical requirement in a Scientific Police's ESB initiative the {\it security} of the transported
information, all information flow in the department require security. This requirement is even more
important when it's considered the exchange of information to outside the Police Department.
%\cite{perfil-seguranca}

Other important requirement is the {\it low couple} between the services, the Espírito Santo's Police 
Department lacks a proper IT staff, so there are several systems brought from third party companies. 
Today, these systems have their's owns data models and interfaces, this situation makes very difficult
the information exchange among them. The ESB proposal address this need establishing a common interface
to information exchange. Also it can maintain the legacy systems easily, by wrapping such systems as services on the ESB. This is also a strong requirement because with a reduced IT team
dealing with software environment changes is a big deal. A service bus can make this management much 
more reliable. The standard provided by the definition of a service bus can also benefits the 
Police Department's software acquisition process. Today the process is not properly defined and 
susceptible to political factors an ESB standard could minimize these aspects of their's software 
acquisition process.    

{\it Reliability}, is a requirement important to a Scientific Police's ESB once it had been deployed
it shall be reliable to the department in such way that critical services to the business process
must be replicated and available in case of fails. For instance, all services involved in the 
Criminal and Civil Identification Processes must be reliable because this process are often executed
and are important to the business. So this critical services must be replicated in the organization
software environment. In this context, the role of an ESB to this requirement is to provide connection
pooling capabilities to it's services. Currently ESB implementations also provide, besides the connection
pooling, load distribution functionalities. This can be a interesting resource to the Scientific Police
but at the moment it is not a critical requirement.

A non functional requirement that has been observed is the definition of a service bus created to agree
with the polices defined by the e-PING\cite{eping} standard. As presented in section \ref{sec:eping} at
the moment, the adoption is only required for federation organs. So, there is no formal requirement 
to it's adoption by the Scientific Police. But, as a federal government initiative it is prudent take
the standard in consideration in any government organs' systems integration approach.
